Skip to content

Conversation

@KhushiPandey8
Copy link
Contributor

What:
Extended the Emoji Key list with additional emojis and categories like community, social, and legal.

Why:
To reflect new contribution types such as community support, social media promotion, and legal compliance.

How:
Updated the emoji-key list in the contributing documentation with the following emojis:

  • 🔊 audio | Audio (Development) | Podcasts, background music, or sound effects
  • 📝 blog | Blogposts (Content) | Links to the blogpost
  • 📖 doc | Documentation (Documentation) | Wiki, README, API Docs
  • 🎨 design | Design (UI/UX) | Logo, branding, UI improvements
  • 🤝 community | Community Support (Community) | Helping users, moderating discussions
  • 💰 sponsor | Sponsorship (Financial) | Funding, grants, donations
  • 📱 social | Social Media (Promotion) | Sharing on social media, marketing efforts
  • ⚙️ ci | CI/CD (DevOps) | Contributions to automated workflows, GitHub Actions
  • ⚖️ legal | Legal (Compliance) | Licensing, GDPR, security policies

Checklist:

  • Documentation
  • Ready to be merged
  • Added myself to contributors table.
    Bot Usage

Extended This Emoji-key list
Improve the readability and utility of the document
@lwasser lwasser added the documentation Documentation related issue/PR label Aug 28, 2025
@lwasser
Copy link
Member

lwasser commented Sep 13, 2025

@all-contributors please add @KhushiPandey8 for docs

@allcontributors
Copy link
Contributor

@lwasser

I've put up a pull request to add @KhushiPandey8! 🎉

@lwasser lwasser changed the title Update emoji-key.md docs: Update emoji-key.md with missing emoji types Sep 13, 2025
@lwasser lwasser changed the title docs: Update emoji-key.md with missing emoji types docs: Update emoji-key.md with updated emoji types Sep 13, 2025
@lwasser
Copy link
Member

lwasser commented Sep 13, 2025

Similar to the previous PR that I merged, we should merge this and then pull it into our docs-upgrade branch via a cherry pick . so i'm not going to merge until i'm ready to do that so we don't lose the updates. Thank you @KhushiPandey8 for this PR!! ❤️

@lwasser
Copy link
Member

lwasser commented Sep 13, 2025

Oops - it looks like we need to lint the pr as well before we can merge.

@JimMadge
Copy link
Member

@lwasser I think we need to think about whether these new contribution types overlap with the existing types, and if they have been implemented in the CLI/app before adding to the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Documentation related issue/PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants